-
Notifications
You must be signed in to change notification settings - Fork 3
Separate unit/API tests and enhance integration test coverage #242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: development
Are you sure you want to change the base?
Separate unit/API tests and enhance integration test coverage #242
Conversation
- Configure Surefire to run API tests (*IT.java) by default - Add 25+ new integration tests (GcpRegion, GlobalFields, Taxonomy) - Update send-report.sh for automated Slack reporting - Add maven-surefire-report-plugin for HTML reports API tests: mvn clean test Unit tests: mvn clean test -Dtest='Test*' jacoco:report
|
We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the staging branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch. |
|
We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the staging branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch. |
…arious parameters and scenarios
… additional edge cases and validation scenarios.
…, configurations, factory methods, headers, and various edge cases.
…TestStack class, covering various scenarios including disabled live preview, null parameters, and parameter assignment.
…s, JSON handling methods, edge cases, and token validation scenarios.
…uilding methods, method chaining, and various edge cases.
…TestStack and TestTaxonomy classes, streamlining test coverage.
… plugins and validating their request/response handling in the Contentstack environment.
…er handling, error setting, and URL parameter conversion, enhancing overall test coverage.
…y, and QueryResult classes, focusing on exception handling, validation scenarios, and edge cases to enhance overall test coverage.
… sending command in send-report.sh
…eaterThanOrEqualTo method, covering various scenarios including null keys, existing keys, chaining, and different value types to enhance test coverage.
…Hub Actions for unit testing with coverage checks
📊 Unit Test Coverage Report
|
…eneration and verification steps, ensuring coverage reports are created and validating their existence before badge generation.
…ring creation with character array for long values and update list creation to use Arrays.asList for better readability and compatibility.
… paths and adjust test execution parameters to ensure accurate coverage reporting and validation.
…treamline coverage checks
…ge checks with output variables, and add PR comment for coverage summary.
…mprove JaCoCo coverage checks with XML report validation, and ensure consistent execution of coverage summary and report upload steps.
…setup to version 9 with Zulu distribution, streamline coverage extraction from JaCoCo HTML report, and enhance PR comment formatting for coverage summary.
…rin distribution and enable Maven caching.
|
Coverage Summary
|
API tests: mvn clean test
Unit tests: mvn clean test -Dtest='Test*' jacoco:report